Implement Sigstore signing and verification of models #276
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Supports all payloads, although in the future we will deprecate most of them, as these are created to migrate existing
serialize_v0
/serialize_v1
implementation and to experiment with UX and benchmarking.Each commit can be reviewed individually. In order these are:
from_str
method tomanifest.Shard
: Adds a method toShard
class to ease parsing a signature back to manifest. Adds tests.sigstore-python
. So, we use a default name of"."
when another cannot be provided.SigstoreSignature
for storing Sigstore signatures: as it says on the tin, just one simple class to allow saving and loading of SigstoreBundle
s.TODO: add tests for signing and verification, in a subsequent PR.
Release Note
NONE
Documentation
NONE